Clarify compute-sanitizer warnings#244
Merged
dunnoconnor merged 1 commit intomainfrom Apr 21, 2026
Merged
Conversation
BradLarson
approved these changes
Apr 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated puzzle_10/memcheck.md
Lines 169–189: The "Verification" expected-output block now shows the actual crash output (segfault stack dump, "intermediate process terminated by signal 11") that users will see before the clean program output — matching exactly what issue #218 reports. A callout note immediately below the block explains it's expected and harmless.
Line 213: The vague "You may see Mojo runtime warnings" note is replaced with a specific explanation that names the segfault, identifies it as a known Mojo/compute-sanitizer injection library conflict, and tells users the ERROR SUMMARY line is still the authoritative result.
Closes Issue #218